This file documents GNUS, the GNU Emacs newsreader.
Copyright (C) 1989, 1990, 1993 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies.
Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.
Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can read netnews within Emacs using the GNUS package. GNUS uses the NNTP protocol to communicate with a news server, which is a repository of news articles. This need not be the same computer you are logged in on.
While the author of GNUS recommends pronouncing it as “news”, we recommend pronouncing it as “gnoose”, to avoid confusion.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| 0.2.1 Getting Started GNUS | How to get started GNUS. | |
| • Local News Spool | How to use a local news spool. | |
| • Private Directory | How to read a private directory. |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
To start GNUS, type M-x gnus.
Run GNUS using the default NNTP server.
Run GNUS without using the default NNTP server.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Somehow or other, GNUS has to know how to find the current netnews. Usually this means it has to know the hostname of the NNTP server.
There are several ways that GNUS can get this information. Most often,
it comes from the environment variable NNTPSERVER. You can
specify a default when you install Emacs by setting the variable
gnus-nntp-server in the ‘site-init.el’ file. If
neither this default nor the environment variable is defined, then GNUS
reads the server name using the minibuffer when you start it.
You can override the default by specifying a prefix argument for the
gnus command. Then it always reads the hostname to use.
GNUS can also bypass NNTP and read the news directly from the file system. This reduces the overhead, but the features for retrieving by their message IDs may fail to work (see section Local News Spool Specific Variables). To do this, specify ‘::’ as the NNTP server “machine name”.
You can also specify a subdirectory of your home directory to use as the current news spool. To do this, specify a colon and the subdirectory name as the NNTP server “machine name”. For example, ‘:Mail’ says to use the directory ‘~/Mail’ as the news spool. This makes it possible to read mail stored in MH folders or articles saved by GNUS. The files in the directory with numeric names are considered news articles, and the other files in the directory are ignored.
A server specific startup file for each directory must exist before you start GNUS. For example, a startup file for the directory ‘~/Mail’ should be a file named ‘.newsrc-:Mail’. See section The Startup File, for more information on the server specific startup file.
Each news server has its own active file which lists the numbers of the active articles in each newsgroup. Reading this file from the server is among the first things GNUS does when it starts. Commands such as g that report additional newly-arrived articles work by rereading the active file.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNUS uses three Emacs buffers: the Newsgroup buffer, the Summary buffer,
and the Article buffer. Each has its own particular purpose and its own
major mode. GNUS often displays all three buffers at the same time,
with a configuration you can customize by setting the variable
gnus-window-configuration.
The Article buffer is where GNUS displays the text of an article. Its major mode is always Article Mode. Users rarely select this buffer because you can read the text while keeping the Summary buffer selected.
| 0.2.4 Newsgroup Buffer | A buffer for listing newsgroups. | |
| 0.2.5 Summary Buffer | A buffer for listing subjects and other important headers. |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Newsgroup buffer contains a list of newsgroups. Its major mode is Group Mode. This is the first buffer that GNUS displays when it starts up.
Normally the list contains only the newsgroups which you subscribe to and which contain unread articles. It is normally empty if there is no such newsgroups. When you start GNUS, it displays the message ‘No news is good news.’ in the echo area.
The format of the Newsgroup buffer looks like this:
sm number: newsgroup
A character indicating whether the newsgroup is subscribed to. ‘U’ means you subscribe to the newsgroup; ‘ ’ means that you don’t. You can change your subscriptions using commands available in Group mode.
A character indicating whether there are newly arrived and unread articles in the newsgroup. ‘*’ means there are no newly arrived articles in the newsgroup. ‘ ’ means there are newly arrived articles.
The number of unread articles in the newsgroup.
The name of the newsgroup.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Summary buffer displays a summary of articles in a single newsgroup, including their subjects, their numbers, and who posted them. Its major mode is Summary mode. GNUS creates a Summary buffer for a newsgroup when you select the group in the Newsgroup buffer.
A Summary buffer contains a line for each article. Each line looks like this:
s number:c[lines:author] subject
Here is what the fields mean:
The status code for this article. ‘ ’ means the article is newly arrived and never read. ‘D’ means you read the article already. ‘-’ means you read it but marked it as saved.
The number assigned to the article.
A character indicating which article is currently selected. ‘+’ is placed on the current article.
The number of lines of the article body.
The mail address of the author of the article.
The subject of the article.
You can customize the format by setting the variable gnus-optional-headers.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Newsgroup buffer normally lists the newsgroups which you subscribe to and which contain unread articles. But not always—some of the things you can do display additional newsgroups. The commands available in this buffer are mostly concerned with subscribing and unsubscribing.
| 0.3.1 Browsing Newsgroups | Moving around in the Newsgroup buffer. | |
| 0.3.2 Selecting a Newsgroup | Selecting a newsgroup to read articles. | |
| • Maintenance | Maintaining newsgroups. | |
| 0.3.4 Exiting GNUS | How to exit GNUS. | |
| 0.3.5 Miscellaneous Commands | Other miscellaneous commands. |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Most of the newsgroup commands operate on the group described by the current line. To use them, you need to move the cursor to the group you want to act on. You can use ordinary Emacs motion commands, or these special commands:
Move point to the next newsgroup containing unread articles
(gnus-group-next-unread-group).
Move point to the previous newsgroup containing unread articles
(gnus-group-prev-unread-group).
Move point to the next newsgroup (gnus-group-next-group).
Move point to the previous newsgroup (gnus-group-prev-group).
Move point to the newsgroup specified by name
(gnus-group-jump-to-group).
Move point to the beginning of the buffer (beginning-of-buffer).
Move point to the end of the buffer (end-of-buffer).
Restrict visible newsgroups to the current region specified by point
and the mark (gnus-group-restrict-groups).
The command j (gnus-group-jump-to-group) reads a
newsgroup name interactively, and moves point to it. If there is no
such newsgroup in the buffer, a line for the newsgroup is inserted at
the beginning of the buffer.
The command r (gnus-group-restrict-groups) restricts
visibility in the Newsgroup buffer to the region specified by point and
mark. It is not quite the same as C-x n; it includes all of the
line that the region starts in, and all of the line that the region ends
in. Type C-x w (widen) to widen visibility to the whole
buffer.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
To start reading the articles in a newsgroup, move to that newsgroup
in the Newsgroup buffer and type SPC
(gnus-group-read-group) or =
(gnus-group-select-group).
Select the newsgroup at point, and then select the first unread article
automatically (gnus-group-read-group).
Select the newsgroup at point (gnus-group-select-group).
Normally, when you select a newsgroup, GNUS prepares to read only the
unread articles (including saved articles). If the newsgroup has no
unread articles and you select it anyway, GNUS prepares to read all the
articles. You can force GNUS to include all the articles by giving a
prefix argument to the commands SPC and =
(gnus-group-read-group and gnus-group-select-group).
If the number of articles being selected is larger than the variable
gnus-large-newsgroup, GNUS prompts for the number of articles to
prepare. If your answer n is positive, GNUS prepares the last
n articles. If n is negative, GNUS prepares the first
-n articles. If you answer with the empty string, GNUS
prepares all articles.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This section explains how to subscribe and unsubscribe, as well as other related activities. Most of the commands operate on the newsgroup listed on the current line.
Mark all newly arrived articles in the newsgroup as read, but don’t
alter articles explicitly marked as saved
(gnus-group-catchup).
Mark all articles in the newsgroup as read
(gnus-group-catchup-all).
Show only the newsgroups which you now subscribe to and which now
contain unread and saved articles (gnus-group-list-groups).
Show all newsgroups available on your news server
(gnus-group-list-all-groups).
Unsubscribe from (or subscribe to) the newsgroup
(gnus-group-unsubscribe-current-group).
Unsubscribe from (or subscribe to) the newsgroup named newsgroup
(gnus-group-unsubscribe-group).
Kill the newsgroup line that point is in
(gnus-group-kill-group).
Kill newsgroups in current region (excluding current line)
(gnus-group-kill-region).
Yank the last newsgroup killed (gnus-group-yank-group). It is
inserted just before the current line. Successive uses of C-y
yank earlier kills, in last-in first-out order.
Exchange current newsgroup and previous newsgroup.
(gnus-group-transpose-groups).
Display a list of the newsgroups you have killed. This is so you can copy them back into the startup file.
Delete bogus newsgroups (gnus-group-check-bogus-groups).
Get newly arrived articles for all groups
(gnus-group-get-new-news).
The commands c and C (gnus-group-catchup and
gnus-group-catchup-all) mark all or most of the articles in a
newsgroup as read. They are useful if you have been away from news
reading for a while, and you don’t want to slog through the backlog of
old postings. These commands do not take account of the cross-reference
information in the ‘Xref:’ field, while the c command in
Summary Mode does.
Only subscribed newsgroups containing unread and saved articles are usually
displayed in the Newsgroup buffer. Type L
(gnus-group-list-all-groups) to show all newsgroups which are
currently active. Use l (gnus-group-list-groups) to go
back to the usual contents—only groups which have news for you to
read.
The command U (gnus-group-unsubscribe-group) reads a
newsgroup name interactively, and toggles its subscription flag. This
is the usual way to subscribe to new groups. (You can also type L
and then use u on the groups you want to read.) You can also
arrange to subscribe automatically to some or all newly created
newsgroups using the options line in your startup file.
The command C-k (gnus-group-kill-group) kills a newsgroup
from both the Newsgroup buffer and the raw startup file. If you change
your mind, type C-y (gnus-group-yank-group); this yanks the
last newsgroup killed with the C-k command.
The command C-c C-l (gnus-list-killed-groups) pops up a buffer listing
the newsgroups you have killed. You can yank any of these newsgroups by
moving point to the entry for the newsgroup you want, and then typing
y or C-y (gnus-browse-killed-yank). So a convenient
way to change the order of newsgroups is to kill some of them, then go
to the list of killed groups and yank them in the order you want.
You are not limited to yanking only the groups that you killed in the current GNUS session. All the groups you have ever killed are remembered in the quick startup file, and you can restore them any time unless you lose the file.
A bogus newsgroup is one not in the list of active newsgroups in
the active file. Type b (gnus-group-check-bogus-groups) to
delete all the bogus newsgroups that you subscribe to. Bogus newsgroups
that you have unsubscribed or killed are deleted also.
The g command rereads the active file to get updated lists of articles available to be read.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Suspend the current GNUS session
(gnus-group-suspend).
Update the startup file ‘.newsrc’, and then exit GNUS
(gnus-group-exit).
Exit GNUS without updating the startup file ‘.newsrc’
(gnus-group-quit).
Suspending GNUS with z (gnus-group-suspend) kills all
GNUS buffers except for the Newsgroup buffer. To resume again, switch
to the Newsgroup buffer and type g
(gnus-group-get-new-news) to get newly arrived articles. It is a
good idea to update the startup file (see section The Startup File) before
suspending GNUS.
If you want to forget what you read this GNUS session, exit GNUS by
the command Q (gnus-group-quit). Otherwise, exit by the
command q (gnus-group-exit) to update the startup
file.
The hook gnus-exit-gnus-hook is called when exiting GNUS, and
the hook gnus-suspend-gnus-hook is called when suspending GNUS.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Other miscellaneous Group mode commands are described here.
Compose a new article (gnus-group-post-news). @xref{Followup and
Reply}, for more information.
Edit a local kill file (gnus-group-edit-local-kill). See section Kill File, for more information.
Edit your global kill file (gnus-group-edit-global-kill).
See section Kill File, for more information.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Summary buffer shows you a summary of the contents of a single newsgroup, with one line for each article. You can move around in the Summary buffer, giving commands to view articles, save them, reply to them, and so on. When you view an article, its text appears in a separate buffer, but the Summary buffer remains current. In fact, there is hardly ever a reason to select the Article buffer; you can do almost all news reading tasks while staying in the Summary buffer.
| 0.4.1 Reading Articles | How to read articles. | |
| 0.4.2 Searching Articles | Searching for articles. | |
| 0.4.3 Referencing Articles | Referencing parent articles. | |
| 0.4.4 Saving Articles | Saving articles in your favorite format. | |
| 0.4.5 Sorting Headers | Sorting the Summary buffer. | |
| • Followup and Reply | Followup and reply commands. | |
| 0.4.7 Exiting the Current Newsgroup | How to exit the current newsgroup. |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The most basic command for reading articles is <SPC>
(gnus-summary-next-page). When you are viewing the middle of a
article, <SPC> scrolls the article forward. When you get to the end
of an article, <SPC> advances to the next article. You can read all
the unread articles straight through using just <SPC>.
Naturally, though, there are plenty of more advanced features available.
| 0.4.1.1 Cursor Motion in the Summary Buffer | Special cursor motion commands for Summary. | |
| 0.4.1.2 Commands to Read Articles | Commands for viewing an article differently. | |
| 0.4.1.3 Scrolling Within an Article | Browsing through a message. | |
| 0.4.1.4 Moving Among Articles | Selecting articles. | |
| 0.4.1.5 Marking Articles | Marking articles as (un)read. | |
| 0.4.1.6 Reading Based on Conversation Threads | Reading articles based on conversation threads. | |
| 0.4.1.7 Reading Digest Articles | How to read digest articles. |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
For moving around in the Summary buffer, you can use these special commands as well as the usual cursor motion commands.
Move point to the next header (gnus-summary-next-subject).
Move point to the previous header (gnus-summary-prev-subject).
Move point to the next header, skipping marked articles
(gnus-summary-next-unread-subject).
Move point to the previous header, skipping marked articles
(gnus-summary-prev-unread-subject).
Move point to the line describing an article specified by number with a
prefix argument (gnus-summary-goto-subject).
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
<SPC> in the Summary buffer scrolls the Article buffer to the next
screenful or to the next article (gnus-summary-next-page)
Select the article on the current line
(gnus-summary-show-article). This command always rereads the
article text from the server even if the same article is already
selected.
Expand the Summary buffer’s window to occupy all the screen space that
GNUS is now using (gnus-summary-expand-window).
Toggle truncation of lines in the Summary buffer
(gnus-summary-toggle-truncation).
Stop page breaking of article buffer (gnus-summary-stop-page-breaking).
Show all headers of the current article if pruned header currently
shown, or vice versa (gnus-summary-toggle-header).
Toggle MIME processing (gnus-summary-toggle-mime).
Caesar rotate letters by 13 places and Japanese characters by 47 places
(gnus-summary-caesar-message).
The command = (gnus-summary-expand-window) expands the
Summary window by deleting the Article window. Use it when you want to
concentrate on the Summary buffer. This command is different from
C-x 1 when more than two windows exist.
The command C-c C-r (gnus-summary-caesar-message) rotates
all letters in the body of the current article by 13/47 places. (This
encoding is often called “rot 13”.) To undo this operation, run it a
second time.
If an article contains multiple pages, GNUS normally displays just one page at a time. To advance to the next page of an article, simply type <SPC>. It advances to the next page whenever the end of a page is on the screen.
The command w (gnus-summary-stop-page-breaking)
temporarily suspends page breaking; it makes the entire current article
visible. You can turn off page breaking all the time by setting the
variable gnus-break-pages to nil.
Page boundaries are defined by the variable
gnus-page-delimiter, whose value is a regular expression. The
default is to match a formfeed character at the beginning of a line.
GNUS normally hides many uninteresting header fields when it displays
an article. (The variable gnus-ignored-headers controls which
fields are ignored.) If you want to see the whole header, type t
(gnus-summary-toggle-header). Use t a second time to hide
the uninteresting header fields again.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This section describes the commands you can type in the Summary buffer to scroll the Article buffer. (If you want to scroll the Summary buffer, you can use the usual Emacs scrolling commands.)
Scroll to the next page of the current article
(gnus-summary-next-page). Select it first if no article is
selected yet. Select the next unread article automatically at the end of
the message.
Scroll the current article backward (gnus-summary-prev-page).
Scroll the current article one (or n) lines forward
(gnus-summary-scroll-up). A negative argument scrolls backward.
Move point to the beginning of the current article
(gnus-summary-beginning-of-article).
Move point to the end of the current article
(gnus-summary-end-of-article).
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These commands move point in the Summary buffer to a different line and display that line’s article.
Read the next article, skipping marked articles
(gnus-summary-next-unread-article).
Read the previous article, skipping marked articles
(gnus-summary-prev-unread-article).
Read the next article (gnus-summary-next-article).
Read the previous article (gnus-summary-prev-article).
Read the next article with the same subject as the current article
(gnus-summary-next-same-subject).
Read the previous article with the same subject as the current article
(gnus-summary-prev-same-subject).
Read the first unread article
(gnus-summary-first-unread-article).
Read the article selected last (gnus-summary-goto-last-article).
If you repeat l, it keeps moving to articles that you read
longer and longer ago.
If the variable gnus-auto-select-same is non-nil, the
commands n and p (gnus-summary-next-unread-article
and gnus-summary-prev-unread-article) skip articles until they
come to another article with the same subject. If you are used to
reading news with ‘rn -S’, set the variable to non-nil to
get familiar behavior.
If the variable gnus-auto-extend-newsgroup is non-nil,
the commands N and P (gnus-summary-next-article and
gnus-summary-prev-article) extend visible articles to forward and
backward if possible. The Summary buffer normally displays just a
subset of the extant articles; extending the buffer means that if you
try to move forward from the last article shown, it looks for later
articles that are not shown, and puts them into the buffer so you can
move to them.
The variable gnus-auto-select-next defines the behavior of GNUS
when there is no unread article in the current newsgroup and a command
selecting the next unread article is executed. If the variable is
non-nil, the next newsgroup containing unread articles is
selected automatically.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNUS uses single-character marks to indicate the status of an article.
A newly arrived article.
An article marked as saved.
An article marked as read.
Both newly arrived articles and saved articles are considered unread.
The status is displayed at the beginning of each line of the Summary buffer. Here are some commands for changing these marks:
Mark this line’s article as read, then move point to the following line
(gnus-summary-mark-as-read-forward). This and the following similar
commands do not select an article; they only move point in the Summary
buffer.
Mark this line’s article as saved, then move point to the following line
(gnus-summary-mark-as-unread-forward).
Clear marks on this line’s article, then move point to the next line
(gnus-summary-clear-mark-forward). This sets the status to
“newly arrived”.
Analogous to d, u and M-u, except that they move backwards instead of forwards in the Summary buffer.
Mark as read all articles with the same subject as the current article,
then select the next unread article
(gnus-summary-kill-same-subject-and-select). Use this when you
decide a certain discussion is not interesting.
Mark as read all articles with the same subject as the current article
(gnus-summary-kill-same-subject).
Mark all newly arrived articles as read; then exit the current newsgroup
(gnus-summary-catchup-and-exit). This does not change the
status of articles that are saved.
Mark all articles (including saved articles) as read, and then exit the current newsgroup.
Mark all newly arrived articles as read, but don’t alter saved articles.
Mark all articles as read.
Delete summary lines for articles marked as read
(gnus-summary-delete-marked-as-read).
Delete headers marked with any of marks
(gnus-summary-delete-marked-with).
You can make it easier to see the remaining unread articles in the
Summary buffer by deleting the lines describing the already read
articles. To do this, use the command x
(gnus-summary-delete-marked-as-read). The command X
(gnus-summary-delete-marked-with) deletes headers which have
certain specified marks. Thus, X D - <RET> deletes all
articles marked with ‘D’ or ‘-’—which is to say, all read
and saved articles. (There are no spaces in that command; we inserted
spaces for clarity when showing it here.)
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A thread is defined as a set of articles related by cross-reference. These references make use of header fields ‘References:’ and ‘In-Reply-To:’, which cite the message ID of another article.
Conversations in a newsgroup usually contain several threads under a single subject. This makes it difficult to know which article follows which without reading references directly. You can use the thread-based commands to do this automatically. You can follow threads of conversation, mark entire threads as read, and go up and down thread trees.
The command M-C-t (gnus-summary-toggle-threads) toggles
showing conversation threads in Summary mode. If it is turned on,
Summary buffer is displayed in a tree structured form which shows the
thread structure.
Toggle thread-based reading
(gnus-summary-toggle-threads).
Show the thread subtree of the current line
(gnus-summary-show-thread).
Show all thread subtrees.
Hide the thread subtrees of the current line
(gnus-summary-hide-thread).
Hide all thread subtrees.
Go to the next thread at the same level
(gnus-summary-next-thread).
Go to the previous thread at the same level
(gnus-summary-prev-thread).
Go down to next thread subordinate to the current line.
(gnus-summary-down-thread).
Go up to the parent thread of the current line
(gnus-summary-up-thread).
Mark all articles under current thread as read
(gnus-summary-kill-thread).
Thread subtrees can be hidden by using the command C-M-h
(gnus-summary-hide-thread), and the hidden subtrees can be shown
by using the command C-M-s
(gnus-summary-show-thread).
If the variable gnus-thread-hide-killed is non-nil,
thread subtrees killed by the command C-M-k
(gnus-summary-kill-thread) are hidden automatically.
If you want to hide thread subtrees initially, set the variable
gnus-thread-hide-subtree to non-nil.
If you want to enable thread-based reading automatically, set the
variable gnus-show-threads to non-nil.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Digest article is a message containing many messages in digest format. Since a digest article contains many messages in one article, it is a little bit difficult to read it on a per message basis. The following commands make it easier to read each message in a digest.
Scroll to the next digest message of the current article
(gnus-summary-next-digest).
Scroll to the previous digest message of the current article
(gnus-summary-prev-digest).
Read the current digest article using Rmail
(gnus-summary-rmail-digest).
The commands C-c C-n and C-c C-p
(gnus-summary-next-digest and gnus-summary-prev-digest)
scroll a digest article to the next and previous digested message,
respectively. The variable gnus-digest-separator specifies a
regexp which separates digested messages.
The command C-d (gnus-summary-rmail-digest) runs Rmail on
a digest article and makes it possible to read messages not in digest
form using Rmail Mode. @xref{Rmail, Rmail, emacs}, for more
information on Rmail Mode. Use the hook gnus-select-article-hook
to run Rmail on digest articles automatically.
Some newsgroups use a digest format that cannot be read using Rmail.
In this case, C-d displays ‘Article is not a digest’ in the
echo area. It is, however, possible to read these incomplete digest
articles by modifying the message headers or bodies appropriately using
the hook gnus-select-digest-hook. See section Function Hooks, to modify
incomplete digest articles.
If the variable gnus-digest-show-summary is non-nil, a
summary of the digest article is also displayed automatically when Rmail
is invoked.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Do incremental search on the current article
(gnus-summary-isearch-article).
Search for articles containing a match for regexp forward
(gnus-summary-search-article-forward). If regexp is empty,
the last regexp used is used again.
Search for articles containing a match for regexp backward
(gnus-summary-search-article-backward). If regexp is empty,
the last regexp used is used again.
Execute command on articles containing a match for regexp in
field of the headers (gnus-summary-execute-command). If
field is empty, the entire article is searched for.
The command s (gnus-summary-isearch-article) does an
incremental search on the current article. This is like switching to
the Article buffer and typing C-s except that the Summary buffer
remains selected. The command M-s
(gnus-summary-search-article-forward) searches for articles
containing a match for regexp. The search starts from the current point
of the current article. To search backwards, use the command M-r
(gnus-summary-search-article-backward).
The command & (gnus-summary-execute-command)
interactively reads a header field name, a regular expression, and a
valid key sequence. It then searches for all articles in which that
regular expression matches the contents of the specified header field.
It executes the key sequence in each such message.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Refer to parent of the current article in terms of the ‘References’
field (gnus-summary-refer-parent-article). With a prefix
argument, go back to the child.
Refer to the article by using the Message-ID
(gnus-summary-refer-article).
The command ^ (gnus-summary-refer-parent-article) refers
to parent article of the current article. You can go back to the child
article with C-u ^.
^ and M-^ select a new article without moving point in the Summary buffer. As a consequence, you can use g to go back to the article in which you started the last sequence of ^ and M-^ commands.
You can use the r command in Article mode to follow a reference contained in the text of an article. See section Article Commands.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNUS supports four different formats for saving articles: Rmail format, Unix mailbox format, MH folder, and article format.
Save the current article in Rmail format
(gnus-summary-save-article).
Save the current article in Unix mail file format
(gnus-summary-save-in-mail).
Send contents of the current article through a pipe to a subprocess
running command (gnus-summary-pipe-output).
The variable gnus-default-article-saver controls the formats
used by the o command. By default, it uses Rmail format. If you
set the variable to gnus-summary-save-in-folder, o uses MH
format. If you set it to gnus-summary-save-in-file, o
saves the article text verbatim. The default value is
gnus-summary-save-in-rmail. (All three of these values are
commands that you can bind to other keys.)
The variable gnus-article-save-directory specifies the default
directory for saving articles. If you don’t set this variable
explicitly, it is initialized from the SAVEDIR environment
variable, or, as a last resort, ‘~/News’.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNUS can sort the Summary buffer by number, subject, date, or author of articles.
Sort the headers by number (gnus-summary-sort-by-number).
Sort the headers by subject (gnus-summary-sort-by-subject).
Sort the headers by date (gnus-summary-sort-by-date).
Sort the headers by author (gnus-summary-sort-by-author).
Sorting is stable, which means that it does not disturb the relative order of articles whose sort keys are equal. So you can sort on multiple keys by using several sort commands in a row; the last sort command specifies the most powerful sort key. Thus, C-c C-s C-a C-c C-s C-d C-c C-s C-n sorts by author, and sorts the messages for each author by date, and any messages with the same author and date are sorted by number.
To sort in reverse order, give a prefix argument to the sort commands.
It is also possible to sort the headers automatically when a newsgroup
is selected using the hook gnus-select-group-hook
(see section Function Hooks).
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Compose a new article (gnus-summary-post-news).
Compose a followup to the current article
(gnus-summary-followup).
Compose a followup, and insert the original article right away
(gnus-summary-followup-with-original).
Cancel the current article you posted
(gnus-summary-cancel-article).
Type a (gnus-summary-post-news) to post a new article.
If the variable gnus-interactive-post is non-nil, this
command reads the newsgroup, subject, and distribution interactively.
The command f (gnus-summary-followup) fills these values in
automatically from those of the selected article; thus, the article you
post will be a followup to the selected article.
Type C-c C-y (news-reply-yank-original) to include the
original article in the text of the followup. Unless the original
article is quite short, you should edit it to keep only the particular
sentences you are directly responding to.
The command F (gnus-summary-followup-with-original) yanks
the original article automatically. If you want to followup to several
articles in a single article and want to include them in it, type
F for each of them. You will be asked if a text being edited
should be erased. You should answer ‘n’ to the question.
If the variable gnus-novice-user is non-nil, your
confirmations will be required for composing a new article.
The major mode for composing a new article is News Mode which is
borrowed from ‘rnewspost.el’. Type C-h m
(describe-mode) to get more help on News Mode.
Suppose you post an article and then later realize that you made a
horrible mistake. You really do not want anyone to see your article.
You want the article to be removed from any machines that it may have
reached. The command C (gnus-summary-cancel-article) is
intended to do this. First select the offending article as current,
then type C.
Reply to the author of the current article (gnus-summary-reply).
Reply to the author of the current article with the original article
(gnus-summary-reply-with-original).
Forward current message to someone else.
(gnus-summary-mail-forward).
Compose a mail message in other window (gnus-summary-mail-other-window).
Use the command r (gnus-summary-reply) to mail a reply to
the author of the article. Type C-c C-y to yank the text of the
article you are replying to. The command R
(gnus-summary-reply-with-original) yanks the original article
automatically.
@xref{Mail Mode}, for information on how to finish sending the reply.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Exiting a newsgroup means going back to the Newsgroup buffer and (normally) saving the changes you have made in the status of articles.
Exit the current newsgroup, and return to Group Mode
(gnus-summary-exit). This updates the startup file
to indicate the changes in article status in this newsgroup.
Exit the current newsgroup without saving information about article
status (gnus-summary-quit). The effect is to cancel all the
status changes that took place while you were reading this newsgroup.
Save the article status changes, but keep the newsgroup selected
(gnus-summary-reselect-current-group).
The command C-x C-s (gnus-summary-reselect-current-group)
selects the current newsgroup again after temporary exiting the
newsgroup. If no articles remain unread, all articles in the newsgroup
will be selected. A prefix argument to the command means to select all
articles in the newsgroup.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
GNUS displays one article at a time, in a buffer called the Article buffer. When you select an article, GNUS puts the Article buffer on the screen and displays the article there.
If the Article buffer is not visible, it appears on the screen
whenever you select an article for display. You can specify the height
of the Article buffer as a fraction of the screen height by setting the
variable gnus-window-configuration.
The Article buffer has a special major mode, Article mode. It provides these commands:
Scroll this window forward (gnus-article-next-page).
Scroll this window backward (gnus-article-prev-page).
Select another article by following a cross reference
(gnus-article-refer-article). A cross reference is specified by
a Message-ID included in the text of the article. Move point to a
message ID before using this command.
Return to the previous article from the referenced article
(gnus-article-pop-article).
Reconfigure Emacs windows to show the Summary buffer above the Article
buffer and select the Summary buffer
(gnus-article-show-summary). The occasion to use this
is when you have been editing a message to send or article to post.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Each user who reads news has a file called the startup file which records which groups he or she subscribes to and which articles have been read.
GNUS actually uses two startup files that contain the same information. The raw startup file, named ‘~/.newsrc’, is the master copy of the information; this is the same file that other news readers use, and it is kept in the standard format. The quick startup file contains the same information in a format convenient for Lisp to read. GNUS automatically updates the quick startup file from the raw startup file whenever the latter is newer; but normally it saves time by reading only the quick startup file.
These commands in Group mode operate on the startup files:
Restart GNUS, using the raw startup file instead of the quick one, and
get newly arrived articles (gnus-group-restart).
Update both startup files based on changes you have made in the
Newsgroups buffer (gnus-group-force-update).
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A kill file contains lisp expressions to be applied to a selected newsgroup. The purpose is to mark articles as read on the basis of some set of regexps.
There are two kinds of kill files, global and local. A global kill file is applied to every newsgroup, and a local kill file to a specified newsgroup.
| 0.6.1 Making a Kill File | How to make a kill file. | |
| 0.6.2 Editing Kill Files | How to edit kill files. | |
| • Kill File Example | A real example of a kill file. | |
| 0.6.4 Names of Kill Files | Where kill files are kept in the file system. | |
| 0.6.5 Background Kill Processing | Background kill processing. | |
| 0.6.6 Advanced Kill Processing | Advanced kill processing. |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A kill file is simply a file of Lisp code that is loaded (i.e., evaluated) while the Summary buffer is current. In order to work properly, the contents of the file must be designed to interact properly with GNUS. To make it easier to write a valid kill file, GNUS provides a general function which does the things users typically want to do in a kill file.
(gnus-kill field regexp &optional command all)
The gnus-kill function performs an action on each article that
matches a specified condition.
The two required arguments specify the condition. The argument
field specifies a portion of an article; it is either the name of
a header field to search, or "", which says to search the entire
article body. The argument regexp says what to search for. The
condition is this: an article is eligible if the specified portion of
the article contains a match for regexp.
The argument command says what to do when an article fits the
condition. It is either a valid key sequence in Summary mode, or a Lisp
expression which is a list, or nil. A key sequence stands for
its command definition in Summary mode; it means to execute that
command. A Lisp expression means to evaluate that expression.
nil says to mark the article with the character ‘X’.
If all is omitted or nil, gnus-kill checks only
newly arrived articles for meeting the condition. If all is
non-nil, it checks all articles.
Here as an example is how to mark all articles whose subjects contain the string ‘AI’:
(gnus-kill "Subject" "AI")
If you want to mark articles with ‘D’ instead of ‘X’, you can use the following expression, which works by executing the d command.
(gnus-kill "Subject" "AI" "d")
The usual aim of a kill file is to delete certain articles. The way to
do this is to mark them with ‘X’ and then call
gnus-expunge, like this:
(gnus-expunge "X")
gnus-expunge takes one argument, a string containing a number of
mark characters, and deletes all the lines that are marked with any of
those characters.
It works to use gnus-expunge for the marker ‘D’, but you may
not like what it does, because this prevents you from ever rereading an
article marked as read in a previous session. That’s why the default
marker for gnus-kill is ‘X’ rather than ‘D’.
Searching in the Summary buffer normally ignores case; this includes the
searching inside of gnus-kill. If you do not want to ignore the
case, set the variable case-fold-search to nil.
After GNUS has finished applying the appropriate kill files, if the newsgroup has no articles left, GNUS exits that newsgroup right away.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You can use these GNUS commands to find a kill file for editing:
Edit a local KILL file applied to the current newsgroup
(gnus-summary-edit-local-kill).
Edit a global KILL file applied to all newsgroups
(gnus-summary-edit-local-kill).
The same key sequences (M-k and M-K) are available in Group
mode also, but the commands that implement them are
gnus-group-edit-local-kill and
gnus-group-edit-global-kill.
The major mode of these buffers is Kill-File mode, which is like Emacs Lisp mode but with the following additional commands:
Insert a template of a kill command on subject
(gnus-kill-file-kill-by-subject).
Insert a template of a kill command on author
(gnus-kill-file-kill-by-author).
Evaluate the whole current buffer, but do so with the Summary buffer
current (gnus-kill-file-apply-buffer). This is a convenient way
to try out a kill file you have been editing.
Evaluate the sexp before point in current buffer, but do so with the
Summary buffer current (gnus-kill-file-apply-last-sexp).
Save the kill file and then return to the previous buffer
(gnus-kill-file-exit).
The effects of C-c C-k C-s and C-c C-k C-a depend on how you began editing the kill file. If you gave the command M-k or M-K while in the Summary buffer, then the article that was current at that time supplies the string to search for, from its own subject or author.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This is a real example of a local kill file for newsgroup ‘control’.
;; Apply to the newsgroup `control' if the NNTP server is flab.
(if (string-equal gnus-nntp-server "flab")
(progn
(gnus-kill "Subject" "ihave flab\\|sendme")
(gnus-kill "Subject" "cancel\\|newgroup\\|rmgroup" "d")
(gnus-expunge "X")))
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Kill files are kept in the directory specified by the variable
gnus-article-save-directory; its default value is ‘~/News’.
The variable gnus-kill-file-name specifies the global kill file’s
name within that directory; the default is ‘KILL’.
The name of a local kill file is based on the newsgroup’s name. If the
variable gnus-use-long-file-name is non-nil, then the file
name is ‘newsgroup.KILL’. Otherwise, it is
‘news/group/KILL’, where the subdirectory name is made
from the newsgroup name by changing all periods to slashes.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Kill processing can take a long time. If you don’t want to wait for it, try background kill processing using the following shell command:
emacs -batch -l gnus -f gnus-batch-kill newsgroups…
where newsgroups are newsgroup names separated by whitespace. ‘!’ preceding a newsgroup name means negation, and ‘all’ specifies all newsgroups not yet decided. These interpretations are the same as the options line of the startup file (see section The Startup File).
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Internally, applying kills means to run the hook
gnus-apply-kill-hook. It is called after the Summary buffer is
prepared for a selected newsgroup. The default hook is the function
gnus-apply-kill-file which loads a global kill file and a local
kill file in this order. A different style of the kill processing can
be implemented by customizing this hook.
For example, if you don’t have a global kill file, you can use the following hook which applies only a local kill file. This change can save the time for checking the existence of a global kill file.
;; Get rid of the default hook.
(setq gnus-apply-kill-hook nil)
(add-hook 'gnus-apply-kill-hook
'(lambda ()
;; Apply a local kill file.
(load (gnus-newsgroup-kill-file gnus-newsgroup-name) t nil t)))
(As usual, you can put as many functions as you wish into this hook.
What is not usual is the fact that the hook is not initially empty.
Therefore, if you don’t want the default hook value, you must set the
hook variable to nil.)
In contrast, the following example enables only a global kill file.
;; Get rid of the default hook.
(setq gnus-apply-kill-hook nil)
(add-hook 'gnus-apply-kill-hook
'(lambda ()
;; Apply a global kill file.
(load (gnus-newsgroup-kill-file nil) t nil t)))
Here is an advanced example that drastically reduces the time for applying kill files. This hook does the kill processing directly without loading the kill files.
;; Get rid of the default hook.
(setq gnus-apply-kill-hook nil)
(add-hook 'gnus-apply-kill-hook
'(lambda ()
;; Apply to the newsgroup `control'
;; if the NNTP server is flab.
(and (string-equal gnus-nntp-server "flab")
(string-equal gnus-newsgroup-name "control")
(progn
(gnus-kill "Subject" "ihave flab\\|sendme")
(gnus-kill "Subject" "cancel\\|newgroup\\|rmgroup" "d")
(gnus-expunge "X")))))
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Appendix A describes the variables and hooks for simple customization and the variables for localization.
| A.1 Common Variables | Variables for customizing GNUS. | |
| A.2 NNTP Specific Variables | Variables for localizing NNTP environment. | |
| A.3 Local News Spool Specific Variables | Variables for localizing news spool environment. | |
| A.4 Private Directory Specific Variables | Variables for localizing private directory environment. | |
| A.5 Function Hooks | Function hooks for customizing GNUS. |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
gnus-nntp-serverSpecifies the name of the host running the NNTP server. The variable is
initialized from the NNTPSERVER environment variable. If the
server name is preceded by a colon such as ‘:Mail’, the user’s
private directory ‘~/Mail’ is used as a news spool. @xref{NNTP
Server}, and @pxref{Private Directory}, for more information.
gnus-nntp-serviceSpecifies a service name of NNTP, usually a string "nntp". In a
few instances, it must be the number 119. To use a local news
spool of your machine rather than NNTP, set the variable to nil.
@xref{NNTP Service}, and @pxref{Local News Spool}, for more
information.
gnus-local-domainSpecifies the domain which is the domain part of your mail address
excluding the local host name of your machine. The environment variable
DOMAINNAME is used instead if defined. If the function
system-name returns the full Internet name, there is no need to
define the domain. @xref{Domain,, Domain and Organization}, for more
information.
gnus-local-organizationSpecifies the organization you belong to. The environment variable
ORGANIZATION is used instead if defined. If the value begins
with a slash, it is taken as the name of a file whose contents are read
for the value. @xref{Domain,, Domain and Organization}, for more
information.
gnus-local-timezoneSpecifies the local time zone you belong to. The value can be either a
time zone name such as ‘"JST"’ or a difference in hour from GMT
such as ‘+0900’. If the variable is non-nil, a general time
zone handling package ‘timezone.el’ is used to generate a valid
date for ‘Date:’ field in terms of RFC822. Otherwise, if it is
nil, GNUS generate a date ignoring the local time zone. If you are
using Bnews, it is okay since ‘inews’ will rewrite the invalid
date. However, if you are using Cnews or INN, you must set the variable
to the correct time zone or remove Date from the variable
gnus-required-headers since their ‘inews’ do not rewrite the
wrong ‘Date:’ field.
If you want to display the time of articles in your local time zone,
call the function gnus-gmt-to-local from the hook
gnus-article-prepare-hook.
gnus-local-distributionsSpecifies a list of distributions. The head of the list is used as default. Each element of the list must be a string. If distributions file is available, its content is also used as distributions.
gnus-use-generic-fromNon-nil means the local host name of your machine will not appear
in the ‘From:’ field of article headers. If the variable is a
string, it is used as your domain instead of the definition by the
variable gnus-local-domain or the environment variable
DOMAINNAME. @xref{GENERICFROM}, for more information.
gnus-use-generic-pathNon-nil means the NNTP server name will not appear in the
‘Path:’ field of article headers. If the variable is a string, it
is used in the ‘Path:’ field as the NNTP server name instead of the
definition by the variable gnus-nntp-server. @xref{GENERICPATH},
for more information.
gnus-ignored-newsgroupsSpecify a regular expression used to ignore uninterested newsgroups in the active file. Any lines in the active file matching this regular expression are removed from the newsgroup list before anything else is done to it, thus making them effectively invisible. There is no way to know what newsgroups there are if they are ignored.
gnus-ignored-headersSpecifies header fields which should be ignored in an article.
gnus-required-headersSpecifies header fields which should be included in an article you will post. RFC977 and RFC1036 require From, Date, Newsgroups, Subject, Message-ID and Path fields. Organization, Distribution and Lines are optional. If you want GNUS not to generate some fields, remove them from the variable. If news system is Cnews, you may have to remove Date and to add Lines.
gnus-startup-fileSpecifies a startup file of the Bnews system, usually ‘.newsrc’. If there is a file named ‘.newsrc-server’, it is used instead when talking to server. See section The Startup File, for more information.
gnus-signature-fileSpecifies a signature file of the Bnews system, usually
‘.signature’. The signature file is processed by the function
gnus-inews-insert-signature called from the hook
gnus-prepare-article-hook by default. If there is a file named
‘.signature-distribution’, it is used instead when the
distribution of the article is distribution. Set the variable to
nil to prevent appending the signature file automatically.
gnus-use-cross-referenceSpecifies what to do with cross references (‘Xref:’ field). If it
is nil, cross references are ignored. If it is t,
articles in subscribed newsgroups are only marked as read. Otherwise,
if it is not nil nor t, articles in all newsgroups are
marked as read.
gnus-use-followup-toSpecifies what to do with ‘Followup-To:’ field. If it is
nil, its value is ignored. If it is non-nil, its value is
used as followup newsgroups. Especially, if it is t and you are
going to followup to an article in which poster is specified,
your confirmation is required.
gnus-use-full-windowNon-nil means to take up the entire screen of Emacs. If the
variable is nil, the windows used by GNUS will be restricted to
the bounds of the original window. This is very useful if you want to
read articles while you do other work in other windows.
gnus-window-configurationSpecifies the configuration of the Group Mode window, the Summary Mode window, and the Article Mode window. The window configuration can be specified for each action of GNUS (e.g. selecting a newsgroup or selecting an article). This is quite useful if you are using a slow terminal since the update of Emacs windows can be minimized by displaying these three windows same time.
The variable must be a list of ‘(action (g s
a))’, where action is an action being performed, and
g, s, and a are the relative heights of the Group Mode
window, the Summary Mode window, and the Article Mode window,
respectively. action is summary, newsgroups, or
article.
The following example is the default window configuration:
(setq gnus-window-configuration
'((summary (0 1 0))
(newsgroups (1 0 0))
(article (0 3 10))))
The following is an example of yet another two windows mode. Article buffer is always displayed on a screen. This is useful on a slow terminal.
(setq gnus-window-configuration
'((summary (0 1 0))
(newsgroups (1 0 3))
(article (0 1 3))))
The following is an example of three windows mode. Three buffers are always displayed on a screen. This is also useful on a slow terminal.
(setq gnus-window-configuration
'((summary (1 4 0))
(newsgroups (1 1 3))
(article (1 1 3))))
gnus-large-newsgroupSpecifies the number of the articles which indicates a large newsgroup. If the number of articles in a newsgroup is greater than this value, the number of articles to be selected is asked for. If the given value n is positive, the last n articles are selected. If n is negative, the first n articles are selected. An empty string means to select all articles.
gnus-author-copySpecifies a file name saving a copy of an article posted using
‘FCC:’ field. The variable is initialized from the
AUTHORCOPY environment variable. The specified file name is
inserted in ‘FCC:’ field, so you have a chance to change the file
name or disable saving a copy by editing this field.
The ‘FCC:’ field is processed by the function
gnus-inews-do-fcc called from the hook
gnus-inews-article-hook by default. Unless the first character
of the field is `|', the article is saved to the specified file
using the function specified by the variable
gnus-author-copy-saver. The default function rmail-output
saves in Unix mailbox format. Instead, if the first character is
`|', the contents of the article is send to a program specified
by the rest of the value. For example, articles can be saved in an MH
folder by the following:
(setq gnus-author-copy
"|/usr/local/lib/mh/rcvstore +Article")
gnus-author-copy-saverSpecifies a function to save an author copy to. The function is called
with a file name to save a copy to. The default function
rmail-output saves in Unix mailbox format.
gnus-use-long-file-nameNon-nil means that a newsgroup name is used as a default file
name to save articles to. If it is nil, the directory form of a
newsgroup name is used instead. It is set to nil by default if the
variable system-type is either ‘usg-unix-v’ or
‘xenix’.
gnus-mail-save-namegnus-rmail-save-namegnus-folder-save-namegnus-file-save-nameSpecifies a function generating a file name to save articles to. The
function is called with newsgroup, headers, and optional
last-name. Newsgroup is a string representing the current
newsgroup name. Headers is a vector containing headers of the
current article. Macros and functions accessing contents of the
headers are defined as nntp-header-field and
gnus-header-field, respectively. The following functions
are provided as file name generators by default:
gnus-numeric-save-nameReturn a file name like ‘news.group/number’ or
‘news/group/number’ according to the variable
gnus-use-long-file-name.
gnus-Numeric-save-nameReturn a file name like ‘News.group/number’ or
‘news/group/number’ according to the variable
gnus-use-long-file-name.
gnus-plain-save-nameReturn a file name like ‘news.group’ or
‘news/group/news’ according to the variable
gnus-use-long-file-name.
gnus-Plain-save-nameReturn a file name like ‘News.group’ or
‘news/group/news’ according to the variable
gnus-use-long-file-name.
gnus-folder-save-nameReturn a folder name like ‘+news.group’ or
‘+news/group’ according to the variable
gnus-use-long-file-name.
gnus-Folder-save-nameReturn a folder name like ‘+News.group’ or
‘+news/group’ according to the variable
gnus-use-long-file-name.
gnus-default-article-saverSpecifies a function to save articles in your favorite format using the
command gnus-summary-save-article. The function must be
interactively funcallable. In other words, it must be an Emacs command.
The functions currently provided are as follows:
gnus-summary-save-in-mailSave articles in Unix mailbox format.
gnus-summary-save-in-rmailSave articles in Rmail format.
gnus-summary-save-in-folderSave articles in an MH folder.
gnus-summary-save-in-fileSave articles in article format.
gnus-article-save-directorySpecifies a directory name to save articles in using the commands
gnus-summary-save-in-mail, gnus-summary-save-in-rmail, and
gnus-summary-save-in-file. The variable is initialized from the
SAVEDIR environment variable. Its default value is
‘~/News’.
gnus-kill-file-nameSpecifies a file name of kill file (see section Kill File). Its default value is ‘KILL’.
gnus-novice-userNon-nil means you are a novice to USENET. If it is
non-nil, verbose messages may be displayed or your confirmations
may be required.
gnus-interactive-catchupNon-nil means that your confirmation is required when catching up
a newsgroup in Group mode.
gnus-interactive-postNon-nil means that newsgroup, subject, and distribution are asked
for interactively when composing a new article.
gnus-interactive-exitNon-nil means that your confirmation is required when exiting
GNUS.
gnus-user-login-nameSpecifies your login name. The login name is got from the USER
and LOGNAME environment variables and the function
user-login-name, if undefined.
gnus-user-full-nameSpecifies your full name. The full name is got from the NAME
environment variable and the function user-full-name, if
undefined.
gnus-show-all-headersNon-nil means all headers of an article are shown.
gnus-save-all-headersNon-nil means all headers of an article are saved in a file.
gnus-show-mimeNon-nil means process a MIME message. The message is processed
by the function specified by the variable gnus-show-mime-method.
gnus-show-threadsNon-nil means conversation threads are displayed in a tree
structured form according to references in Summary Mode.
gnus-thread-hide-subjectNon-nil means subjects of lower level threads are hidden if the
thread-based reading is turned on.
gnus-thread-hide-subtreeNon-nil means thread subtrees are hidden initially. If thread
subtrees are hidden, you have to run the command
gnus-summary-show-thread by hand or by using
gnus-select-article-hook to show them.
gnus-thread-hide-killedNon-nil means killed thread subtrees are hidden
automatically.
gnus-thread-ignore-subjectNon-nil means subject differences are ignored but only references
are taken into account in constructing threads trees. If it is
non-nil and thread subtrees are hidden, some commands that work
with subjects may not work properly.
gnus-thread-indent-levelSpecifies indentation level of thread subtrees.
gnus-auto-extend-newsgroupNon-nil means visible articles are automatically extended to
forward and backward if possible when the commands N and P
(gnus-summary-next-article and gnus-summary-prev-article)
are executed in Summary Mode.
gnus-auto-select-firstNon-nil means the first unread article is selected automatically
when a newsgroup is selected. If you’d like to prevent automatic
selection of the first unread article in some newsgroups, set the
variable to nil in the hook gnus-select-group-hook or
gnus-apply-kill-hook (see section Function Hooks).
gnus-auto-select-nextNon-nil means the next newsgroup is selected automatically at the
end of the newsgroup. If the value is t and the next newsgroup is
empty (no unread articles), GNUS will exit Summary Mode and go back to
Group Mode. If the value is neither nil nor t, GNUS won’t
exit Summary Mode but will select the following unread newsgroup. If
the value is ‘quietly’, the next unread newsgroup will be selected
without any confirmations.
gnus-auto-select-sameNon-nil means an article with the same subject as the current
article is selected automatically like ‘rn -S’.
gnus-auto-center-summaryNon-nil means that the cursor is always kept centered in the
Summary Mode window.
gnus-auto-mail-to-authorNon-nil means that inserts ‘To:’ field which is filled with
the author of the article when followuping. Mail is sent using the
function specified by the variable gnus-mail-send-method.
gnus-break-pagesNon-nil means an article is broken into pages at page delimiters.
The page delimiter is specified by the variable
gnus-page-delimiter. This may not work with some versions of GNU
Emacs earlier than version 18.50.
gnus-page-delimiterSpecifies regexp describing line-beginnings that separate pages of
articles. Its default value is "^\^L".
gnus-digest-show-summaryNon-nil means that a summary of digest messages is shown when
reading a digest article using the command
gnus-summary-rmail-digest.
gnus-digest-separatorSpecifies a regexp which separates messages in a digest article.
Changes to this variable only affect the commands
gnus-summary-next-digest and gnus-summary-prev-digest, but
not the command gnus-summary-rmail-digest.
gnus-optional-headersSpecifies a function which generates an optional string displayed in the
Summary buffer. The function is called with an article headers,
and must return a string excluding ‘[’ and ‘]’. Headers
is a vector containing headers of the current article. Macros and
functions accessing contents of the headers are defined as
nntp-header-field and gnus-header-field,
respectively.
GNUS provides two functions as follows:
gnus-optional-lines-and-fromReturn a string like "nnn:author", where nnn is the number of lines in an article and author is the name of the author.
gnus-optional-linesReturn a string like "nnn", where nnn is the number of lines in an article.
See section Function Hooks, to change optional headers according to selected newsgroups.
gnus-info-directorySpecifies a directory where the GNUS Info file is placed. It is not
necessary to change this variable unless you install an Info file in a
directory different from the variable Info-directory.
@xref{Texinfo Manual}, for more information.
gnus-show-mime-methodSpecifies a function to process a MIME message in current buffer. The
function metamail-buffer which process the buffer through
‘metamail’ is called by default.
gnus-mail-reply-methodSpecifies a function to begin composing reply mail messages. The
function will be called with an optional argument which means yank
original article automatically if non-nil. To use Mail Mode, set
the variable to gnus-mail-reply-using-mail. To use mh-e letter
Mode, set the variable to gnus-mail-reply-using-mhe.
gnus-mail-forward-methodSpecifies a function to forward the current message to another user. To
use Mail Mode, set the variable to gnus-mail-forward-using-mail.
To use mh-e letter Mode, set the variable to
gnus-mail-forward-using-mhe.
gnus-mail-other-window-methodSpecifies a function to begin composing mail messages in other window.
To use Mail Mode, set the variable to
gnus-mail-other-window-using-mail. To use mh-e letter Mode, set
the variable to gnus-mail-other-window-using-mhe.
gnus-mail-send-methodSpecifies a function to mail a message too which is being posted as an
article. The message must have ‘To:’ or ‘Cc:’ field. The
value of the variable send-mail-function is the default function
which uses sendmail mail program.
gnus-subscribe-newsgroup-methodSpecifies a function called with a newsgroup name when a new newsgroup is found. GNUS provides the following three functions:
gnus-subscribe-randomlyInserts a new newsgroup at the beginning of newsgroups. Thus, newsgroups are in random order.
gnus-subscribe-alphabeticallyInserts a new newsgroup in strict alphabetic order.
gnus-subscribe-hierarchicallyInserts a new newsgroup in hierarchical newsgroup order.
gnus-subscribe-interactivelyAsks for your decision about a new newsgroup subscription, and inserts it in hierarchical newsgroup order if it is subscribed. Unless, it is killed.
The following two definitions illustrate how to write your favorite subscribing method. The following definition (is the definition of the function gnus-subscribe-randomly) adds new newsgroup at the beginning of newsgroups:
(setq gnus-subscribe-newsgroup-method
'(lambda (newsgroup)
(gnus-subscribe-newsgroup newsgroup
(car (car gnus-newsrc-assoc)))))
Instead, if you want to add new newsgroup at the end of newsgroups, use the following:
(setq gnus-subscribe-newsgroup-method
'(lambda (newsgroup)
(gnus-subscribe-newsgroup newsgroup nil)))
If you want to prevent adding new newsgroups automatically and want to
subscribe them later using the command U
(gnus-group-unsubscribe-group) in the Newsgroup buffer, use the
following:
(setq gnus-subscribe-newsgroup-method
'(lambda (newsgroup) nil)) ;Do nothing.
The following final example must be the most useful for you who want not to add new newsgroups automatically. This definition subscribes a new newsgroup first, and then kills it. The killed newsgroups can be added to the subscription list interactively using Browse-Killed Mode (@pxref{Maintenance}).
(setq gnus-subscribe-newsgroup-method
'(lambda (newsgroup)
(gnus-subscribe-newsgroup newsgroup)
(gnus-kill-newsgroup newsgroup)))
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
nntp-buggy-selectNon-nil means the select routine of your operating system is
buggy. GNUS may hang up while waiting for NNTP server responses. The
problem may be solved by setting the variable to t. @xref{NNTP
Problems}, for more information.
nntp-maximum-requestSpecifies the maximum number of requests to be sent to the NNTP server at one time. GNUS may hang up while retrieving headers of a large newsgroup because sending many requests to the NNTP server without reading replies to them causes deadlock. In this case, set the variable to a lower number. @xref{NNTP Problems}, for more information.
nntp-large-newsgroupSpecifies the number of articles which indicates a large newsgroup. If the number of articles is greater than the value, verbose messages will be shown to indicate the current status.
nntp-debug-readNon-nil means display dots “...” every 10000 bytes of a message
being received. If it is a number, dots are displayed per the number.
Set the variable to nil if you are annoyed about verbose messages
while reading news from slow terminal.
tcp-program-nameSpecifies a program which establishes communications between Emacs and
the NNTP server. Its default value is ‘telnet’. Alternative is
‘tcp’ which is distributed as ‘tcp.c’ with other files of GNUS
(@pxref{Files of GNUS}). If your Emacs has the function
open-network-stream, there is no need to define this variable.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
nnspool-inews-programSpecifies a program to post news. This is default to the variable
news-inews-program which is default to ‘inews’.
nnspool-inews-switchesSpecifies switches for the function nnspool-request-post to pass
to the command ‘inews’ for posting news. Its default value is
("-h").
nnspool-spool-directorySpecifies a directory of a local news spool. This is default to the
variable news-path which is default to ‘/usr/spool/news’.
nnspool-active-fileSpecifies an active file of the system for a local news spool. Its default value is ‘/usr/lib/news/active’.
nnspool-newsgroups-fileSpecifies an newsgroups file of the system for a local news spool. Its default value is ‘/usr/lib/news/newsgroups’.
nnspool-distributions-fileSpecifies an distributions file of the system for a local news spool. Its default value is ‘/usr/lib/news/distributions’.
nnspool-history-fileSpecifies a history file of the system for a local news spool. Its default value is ‘/usr/lib/news/history’. Some machines may not have this file. In this case, commands to refer to articles by Message-IDs will not work at all (see section Referencing Articles).
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
mhspool-list-folders-methodSpecifies a function to fill the current buffer with file and directory
names for a given directory name. The output format must be the same as
that of the Unix command ‘ls -R1’. Two functions
mhspool-list-folders-using-ls and
mhspool-list-folders-using-sh are provided now.
mhspool-list-directory-switchesSpecifies switches for the function mhspool-list-folders-using-ls
to pass to the command ‘ls’ for getting file listings in a private
directory. There should be one entry for each line. Its default value
is ("-R"). Some machines may require the ("-R1") switch.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
gnus-group-mode-hookCalled with no arguments after initializing Group Mode if its value is
non-nil. This hook is intended to customize Group Mode only
once. It is possible to define or change the NNTP server as you like in
this hook since the hook is called before GNUS is connected to an NNTP
server.
gnus-summary-mode-hookCalled with no arguments after initializing Summary Mode if its value is
non-nil. This hook is intended to customize Summary Mode only
once. All sorts of searches in Summary Mode normally ignore the case of
the text they are searching through. If you do not want to ignore the
case, set the variable case-fold-search to nil in this
hook.
The following example shows how to assign the functions
gnus-summary-next-group and gnus-summary-prev-group to
keys in Summary Mode.
(setq gnus-summary-mode-hook
'(lambda ()
(local-set-key "\C-cn" 'gnus-summary-next-group)
(local-set-key "\C-cp" 'gnus-summary-prev-group)))
gnus-article-mode-hookCalled with no arguments after initializing Article Mode if its value is
non-nil. This hook is intended to customize Article Mode only
once.
gnus-kill-file-mode-hookCalled with no arguments after initializing Kill-File Mode if its
value is non-nil.
gnus-browse-killed-mode-hookCalled with no arguments after initializing Browse-Killed Mode if its
value is non-nil.
gnus-open-server-hookCalled with no arguments just before opening a connection to NNTP server
if its value is non-nil.
gnus-startup-hookCalled with no arguments after an NNTP server is successfully connected
to if its value is non-nil. It is possible to change the behavior
of GNUS according to the server.
gnus-group-prepare-hookCalled with no arguments after a list of newsgroups is prepared in the Newsgroup buffer. This hook is intended to modify the buffer.
gnus-summary-prepare-hookCalled with no arguments after list of subjects is prepared in the Summary buffer. This hook is intended to modify the buffer.
gnus-article-prepare-hookCalled with no arguments after an article is prepared in the Article buffer. This hook is intended to modify the buffer. For example, kanji code conversion or un-ROT13/47-ing can be done in this hook.
gnus-select-group-hookCalled with no arguments when a newsgroup is selected. This hook is intended to change the behavior of GNUS according to the selected newsgroup.
The following is an example of sorting the headers listed in the Summary buffer by date and then by subject. Preceding ‘Re:’ of subjects is ignored while comparing subjects.
(setq gnus-select-group-hook
'(lambda ()
;; First of all, sort by date.
(gnus-keysort-headers
(function string-lessp)
(function
(lambda (a)
(gnus-sortable-date (gnus-header-date a)))))
;; Then sort by subject ignoring `Re:'.
(gnus-keysort-headers
(function string-lessp)
(function
(lambda (a)
(if case-fold-search
(downcase (gnus-simplify-subject (gnus-header-subject a) t))
(gnus-simplify-subject (gnus-header-subject a) t)))))
))
The following is an example of simplifying subjects like the
gnus-summary-next-same-subject command does:
(setq gnus-select-group-hook
'(lambda ()
(mapcar (function
(lambda (header)
(nntp-set-header-subject
header
(gnus-simplify-subject
(gnus-header-subject header) 're-only))))
gnus-newsgroup-headers)))
In some newsgroups, author names are meaningless. It is possible to prevent listing author names in the Summary buffer as follows:
(setq gnus-select-group-hook
'(lambda ()
(cond ((string-equal "comp.sources.unix"
gnus-newsgroup-name)
(setq gnus-optional-headers
(function gnus-optional-lines)))
(t
(setq gnus-optional-headers
(function
gnus-optional-lines-and-from))))))
gnus-select-article-hookCalled with no arguments when an article is selected if its value is
non-nil.
The default hook definition shows conversation thread subtrees of the selected article automatically as follows:
(setq gnus-select-article-hook
'(lambda ()
(gnus-summary-show-thread)))
It is possible to run Rmail on a digest article automatically as follows:
(setq gnus-select-article-hook
'(lambda ()
(gnus-summary-show-thread)
(cond ((string-equal "comp.sys.sun"
gnus-newsgroup-name)
(gnus-summary-rmail-digest))
((and (string-equal "comp.text"
gnus-newsgroup-name)
(string-match "^TeXhax Digest"
(gnus-header-subject
gnus-current-headers)))
(gnus-summary-rmail-digest)
))))
gnus-select-digest-hookCalled with no arguments when reading digest messages using Rmail if its
value is non-nil. This hook is intended to modify an article so
that Rmail can work with it. See section Reading Digest Articles, for more
information on digest articles.
The following example is the default hook definition to modify incomplete digest articles:
(setq gnus-select-digest-hook
'(lambda ()
;; Reply-To: is required by
;; `undigestify-rmail-message'.
(or (mail-position-on-field "Reply-to" t)
(progn
(mail-position-on-field "Reply-to")
(insert (gnus-fetch-field "From"))))))
gnus-rmail-digest-hookCalled with no arguments when reading digest messages using Rmail if its
value is non-nil. This hook is intended to customize Rmail Mode
for reading digest articles.
gnus-apply-kill-hookCalled with no arguments when a newsgroup is selected and the Summary
buffer is prepared if its value is non-nil. This hook is intended
to apply kill files to the selected newsgroup. It is set to the
function gnus-apply-kill-file by default.
Since a general kill file is too heavy to use only for a few newsgroups, a lighter hook function is recommended. For example, if you’d like to apply kills to articles which contain the string ‘rmgroup’ in subject in newsgroup ‘control’, you can use the following hook:
(setq gnus-apply-kill-hook
'(lambda ()
(cond ((string-match "control" gnus-newsgroup-name)
(gnus-kill "Subject" "rmgroup")
(gnus-expunge "X")))))
See section Kill File, for more information on kill files.
gnus-mark-article-hookCalled with no arguments when an article is selected for the first time
if its value is non-nil. The hook is intended to mark an article
as read (or saved) automatically when it is selected.
The following example is the default definition of the hook:
(setq gnus-mark-article-hook
'(lambda ()
;; Mark the selected article as read.
(or (memq gnus-current-article gnus-newsgroup-marked)
(gnus-summary-mark-as-read gnus-current-article))
;; Put "+" on the current subject.
(gnus-summary-set-current-mark "+")
))
It is possible to mark as saved (‘-’) instead when an article is selected as follows:
(setq gnus-mark-article-hook
'(lambda ()
;; Mark the selected article as saved.
(gnus-summary-mark-as-unread gnus-current-article)
;; Put "+" on the current subject.
(gnus-summary-set-current-mark "+")
))
gnus-prepare-article-hookCalled with no arguments after preparing message body, but before
preparing header fields which is automatically generated if its value is
non-nil. Text changes made by this hook does not affect on the
editing text. The default hook inserts a signature file by calling the
function gnus-inews-insert-signature.
gnus-inews-article-hookCalled with no arguments before posting an article if its value is
non-nil. This hook is called just before sending an article to
the NNTP server or calling the ‘inews’ program. Text changes made
by this hook does not affect on the editing text. It is no recommended
to alter the number of lines of the article since ‘Lines:’ field
may be already there. The default hook does FCC (save an article to the
specified file) by calling the function gnus-inews-do-fcc.
gnus-exit-group-hookCalled with no arguments when exiting the current newsgroup if its value
is non-nil. If your machine is so slow that exiting from Summary
Mode takes a long time, you can inhibit marking articles as read by
using cross-reference information in the ‘Xref:’ field by setting
the variable gnus-newsgroup-headers to nil in this
hook.
gnus-exit-gnus-hookCalled with no arguments when exiting GNUS if its value is
non-nil. If you want to clear out Emacs buffers which were
created by GNUS and remain afterwards, you can use this hook.
The following example shows how to kill a buffer which was used for posting news.
(setq gnus-exit-gnus-hook
'(lambda ()
;; Kill a buffer used for posting news.
(and (get-buffer "*post-news*")
(kill-buffer "*post-news*"))))
gnus-suspend-gnus-hookCalled with no arguments when suspending GNUS if its value is
non-nil. The purpose is the same as the hook
gnus-exit-gnus-hook.
gnus-save-newsrc-hookCalled with no arguments before saving the startup file ‘.newsrc’
if its value is non-nil. This hook is intended to change the way
of backing up the startup file.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Emacs may hang up while waiting for NNTP server responses. This may
be caused by a buggy select routine of your operating system. If so,
the problem may be solved by loading the source code for the library
‘nntp.el’ instead of running the byte-compiled version. If you
still have problems with it, set the variable nntp-buggy-select
to t.
Emacs may hang up while retrieving headers of a large newsgroup. The
reason is that too many requests have been sent to the NNTP server
without reading replies to them. This causes a deadlock of Emacs and
the server. In this case, the number of requests sent to the server at
one time must be reduced. Set the variable nntp-maximum-request
to a lower value than the default. The optimal value depends on your
computing environment.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are two mailing lists and one USENET newsgroup for discussing GNUS related topics. These are intended for exchanging useful information about GNUS, such as bug reports, useful hooks, and extensions of GNUS. If you have any questions or problems, feel free to ask about them. Suggestions are also welcome.
gnu.emacs.gnusThis is a USENET newsgroup under the gnu.all hierarchy which is concerned with the GNU Project of the Free Software Foundation.
info-gnus-english@tut.cis.ohio-state.eduThis is an Internet mailing list which is gated bi-directionally with the gnu.emacs.gnus newsgroup. English is the official language of the list. Please send subscription requests to:
info-gnus-english-request@tut.cis.ohio-state.edu
info-gnus@flab.Fujitsu.CO.JPThis is a JUNET mailing list. Messages of info-gnus-english and gnu.emacs.gnus are forwarded to this list. English and Japanese are the official languages of the list. Please send subscription requests to:
info-gnus-request@flab.Fujitsu.CO.JP
The major difference between info-gnus-english/gnu.emacs.gnus and info-gnus is the official language. There is no need to subscribe to info-gnus if you cannot read messages written in Japanese since most discussions and important announcements will be sent to info-gnus-english.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you find a bug, it is important to report it and to report it in a way which is useful. If it is a bug of a lisp program, what is the most useful is an exact backtrace information of the lisp program together with the version number of GNUS that you are using.
To make the backtrace information, you must set the Emacs variable
debug-on-error to t before the error happens. A backtrace
obtained from a byte-compiled lisp program is not usually
understandable. To make a human readable backtrace, load the source
program which is not byte-compiled yet and then produce the
error.
See (emacs)Reporting Bugs, for more information.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | &
.
<
=
>
^
|
A B C D F G H J K L M N O P Q R S T U W X Z |
|---|
| Jump to: | &
.
<
=
>
^
|
A B C D F G H J K L M N O P Q R S T U W X Z |
|---|
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | D G M N R S W |
|---|
| Jump to: | D G M N R S W |
|---|
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | A D G I L M N O S T U |
|---|
| Jump to: | A D G I L M N O S T U |
|---|
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | B C I L M R T |
|---|
| Jump to: | B C I L M R T |
|---|
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | .
/
A B C D E F G H I K L M N O P Q R S T U W X Y |
|---|
| Jump to: | .
/
A B C D E F G H I K L M N O P Q R S T U W X Y |
|---|
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
This document was generated on March 29, 2022 using texi2html 5.0.
The buttons in the navigation panels have the following meaning:
| Button | Name | Go to | From 1.2.3 go to |
|---|---|---|---|
| [ << ] | FastBack | Beginning of this chapter or previous chapter | 1 |
| [ < ] | Back | Previous section in reading order | 1.2.2 |
| [ Up ] | Up | Up section | 1.2 |
| [ > ] | Forward | Next section in reading order | 1.2.4 |
| [ >> ] | FastForward | Next chapter | 2 |
| [Top] | Top | Cover (top) of document | |
| [Contents] | Contents | Table of contents | |
| [Index] | Index | Index | |
| [ ? ] | About | About (help) |
where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:
This document was generated on March 29, 2022 using texi2html 5.0.